Coherence-free cache

ABSTRACT

The present invention relates to a cache ( 10 ) and system and method of maintaining cache coherency in a parallel processing system, by tagging ( 13 ) cached data ( 11 ) with the identity of the users or process threads which have access rights to the data. Cache users may see a cache miss even if the data is in the cache, unless they have access rights. The tags can be reset to disallow further access on thread transfer or at the point of synchronisation of process threads.

[0001] This invention relates to a mechanism for performing independent caching of shared data (i.e. information of any form) in multiple places within a parallel processing system.

[0002] Caches are devices or mechanisms in a system (e.g. a computer system) which typically hold copies of parts, or all, of the data (i.e. information of any form) held in a remote shared data store (hereafter referred to as the ‘core storage’) and are located close to the user (e.g. a processing thread) of that data, typically so as to allow faster access to that data. When that data is shared between two or more users and copies exist in one or multiple caches simultaneously then problems can arise when one user changes the data, since other users need to see those changes too. Maintaining up-to-date data in each cache is known as maintaining “cache coherency”.

[0003] Many ways of maintaining cache coherency are possible, but there are three common methods, each of which has disadvantages: One is to communicate the changes to all affected caches. This is very expensive in terms of time and infrastructure if changes are very frequent. Another method is for users to identify, in advance, potential points in time when caches may contain incorrect data for whatever reason, and schedule explicit “cache synchronisations” in which either changes are communicated to all other affected caches or the affected caches are flushed. This is difficult to implement well because the scheduling is dependent on what work needs to be done and this needs to be analysed before starting work. Another method is to ensure that if a datum is to be modified then only one copy of it exists in the system. This reduces the potential for sharing data, so if the datum is shared by a lot of users then time is spent moving the datum around between them.

[0004] It would be advantageous for a cache to allow removal of the visibility of the cache from the users, while not requiring expensive communication between caches, and to allow many users to have simultaneous access to writeable data. Within this document, the statement of invention and claims, the term ‘access ’ to cached data refers to the ability to perform read, write, read/write or any combination of these operations.

[0005] It would be further advantageous for a cache to permit selective access to users who are entitled to use and modify cached data, while refusing access to other users of the cache.

[0006] It is an object of the present invention to provide a cache and method of maintaining cache coherency in a shared memory parallel processing system.

[0007] According to a first aspect of the present invention, there is provided a cache for use in caching data from shared memory in a parallel processing system characterised in that said cache comprises at least one tag associated with said cached data.

[0008] Preferably at least one tag comprises information relating to the access of said cached data selected from a list comprising:

[0009] the identity of a processing thread;

[0010] the identity of a user;

[0011] the identity of a processor; and

[0012] a null value.

[0013] More preferably said information relating to the access of said cached data identifies an entity permitted to access the cached data, or optionally which has previously modified the cached data.

[0014] Preferably the cache further comprises a tag setting means for modifying the contents of said at least one tag.

[0015] More preferably said cache further comprises tag comparing means for comparing the contents of said at least one tag with the identity of the requester of access to said cached data, and a data access means responsive to said tag comparing means for providing access to said cached data.

[0016] Typically, there is provided a parallel processing system comprising:

[0017] at least one processor;

[0018] shared memory; and

[0019] at least one cache.

[0020] Typically, each processor has exclusive use of its own cache.

[0021] According to a second aspect of the present invention, there is provided a method of caching data in a cache from shared memory in a parallel processing system comprising the step of caching data fetched from a shared memory in said cache characterised in that said cache comprises at least one tag associated with said cached data.

[0022] Typically the method further comprises the step of writing data from said cache to said shared memory.

[0023] Preferably at least one tag comprises information relating to the access of said cached data selected from a list comprising:

[0024] the identity of a processing thread;

[0025] the identity of a user;

[0026] the identity of a processor; and

[0027] a null value.

[0028] More preferably, said information relating to the access of said cached data identifies an entity permitted to access the cached data.

[0029] Preferably the method further comprises the step of a tag setting means modifying the contents of said at least one tag.

[0030] Optionally, said tag setting means sets said at least one tag to the identity of the requestor of a cache access.

[0031] Optionally, said tag setting means sets said at least one tag to the identity of a plurality of the processes active on a processor.

[0032] Optionally, said tag setting means sets said at least one tag to a null value.

[0033] Optionally, the method of caching data further comprises the steps of:

[0034] comparing the contents of said at least one tag with the identity of the requester of access to said cached data; and

[0035] depending on the results of said comparison, providing access to said cached data

[0036] Optionally, the method of caching data further comprises the steps of:

[0037] comparing the contents of at least one tag whose contents identify an entity which has previously accessed the cached data with the contents of another tag within said cache; and

[0038] depending on the results of said comparison, writing data from said cache to said shared memory.

[0039] In order to provide a better understanding of the present invention, an embodiment will now be described by way of example only and with reference to the accompanying Figures, in which:

[0040]FIG. 1 illustrates, in schematic form, a cache in accordance with the invention; and

[0041]FIG. 2 illustrates, in schematic form, a multi-processing parallel processing system in accordance with the invention; and

[0042]FIG. 3 illustrates a flowchart describing the response to a request for information from a process thread in accordance with the invention.

[0043] The invention is a cache which functions to maintain cache coherence in a shared memory parallel processing system.

[0044] Although the embodiments of the invention described with reference to the drawings comprise computer apparatus and processes performed in computer apparatus, the invention also extends to computer programs, particularly computer programs on or in a carrier, adapted for putting the invention into practice. The program may be in the form of source code, object code, a code of intermediate source and object code such as in partially compiled form suitable for use in the implementation of the processes according to the invention. The carrier may be any entity or device capable of carrying the program.

[0045] For example, the carrier may comprise a storage medium, such as ROM, for example a CD ROM or a semiconductor ROM, or a magnetic recording medium, for example, floppy disc or hard disc. Further, the carrier may be a transmissible carrier such as an electrical or optical signal which may be conveyed via electrical or optical cable or by radio or other means.

[0046] When the program is embodied in a signal which may be conveyed directly by a cable or other device or means, the carrier may be constituted by such cable or other device or means.

[0047] Alternatively, the carrier may be an integrated circuit in which the program is embedded, the integrated circuit being adapted for performing, or for use in the performance of, the relevant processes.

[0048] With reference to FIG. 1, the cache 10 is implemented in digital logic and comprises cached data 11, which is from a shared main memory 12. The cache also comprises RAM memory tags 13 associated with the RAM memory cached data and tag setting logic 14 for setting or modifying the contents of the tags, a tag comparing logic 15 for comparing the contents of the tag with the identity of entities requesting data from the cache, and a data access logic 16 for providing permitted entities with access to data in the cache.

[0049] All of these “coherence-free caches” in a system can be completely independent, self-contained, and need no information about what any other parts of the system are doing, yet allow data to be shared and changes to be visible to all concerned.

[0050] When multiple users are concurrently active we can assume they are operating asynchronously. When a user accesses data it is important that they see their transactions occurring in a correct order. The transactions of each user may be interleaved with the transactions of the other users, and since the users are asynchronous the interleaving can be assumed to be indeterminate. If one user needs to know when a certain set of transactions of another user has been completed before it attempts to generate more transactions for itself, then those users perform a “time synchronisation” (e.g. a barrier synchronisation, and not to be confused with a cache synchronisation).

[0051] Between time synchronisations each user need have no knowledge of what the other users are doing, nor when they are doing it. It can therefore be assumed that each user does not know if the data it is using is being modified by any other users. In this respect we can safely assume that if no time synchronisation is performed then any modification of shared data is irrelevant and can be ignored. This means that, at the very least, there is no need to communicate any data changes to other caches until a time synchronisation occurs.

[0052] When a user is allowed to access a datum in a cache this is herewith defined as an “access right” to that datum. A user has “access” to a cache (but not necessarily to the data in the cache) if the user can potentially read, write, or modify data within that cache.

[0053] If a user attempts to access data and a copy of that data is held in the cache then it may only access the cached copy if it has access rights to that data. If it does not have access rights then it must access the core storage instead.

[0054] Cached data is associated with its users in order to determine access rights. Such association may typically be implemented by “tagging” each datum in the cache with information identifying the users which have valid access rights to that datum. If, for example, each user has a unique identification code, then a representation of a user's code can be tagged onto the data for which it has access rights. Such a tag may also contain additional information about the access or usage of data. Note that core storage need not have any knowledge of such associations.

[0055] It is permissible for more than one user to have access rights for any single datum. It is also permissible to have a datum, or data, for which no users have access rights. Also, not all data need be associated with its users; such a non-associative arrangement can typically improve storage density if the coherence-free caching scheme is not required for some data, e.g. for read-only constants.

[0056] When a synchronisation occurs we need only ensure that both the core storage is up-to-date and that the synchronising users lose access rights to any cached data which is potentially shared between them. Depending on the behavior required it may also be desirable to remove access rights for other or all users, not only those synchronising.

[0057] When data is taken from core storage and placed in a cache then the data can be assumed to be sufficiently up-to-date and the user (if any) which requested the data can then be given access rights to the cached data. If desired the data can also be made accessible to all current users of that cache.

[0058] When a user first starts using a cache it typically has no access rights to any of the data in that cache. This ensures that the user must go to core storage and therefore collect up-to-date data.

[0059] It is possible for a user to start off at the same point as another user, in which case it is possible, but not necessary, for that user to inherit all the access rights to data from the original user, though from that point onwards the two users are typically considered independent.

[0060] If a user migrates from the domain of one cache into the domain of another cache then it will typically lose access to any cached data in the first cache. This ensures that if the migrated user returns to the first cache it can not see the potentially out-of-date data. It may also be desirable for other users to also lose access to some or all of the data that they share with the migrating user.

[0061] If a user terminates its use of a cache then it will typically lose access to any data within that cache. This ensures that if the user reappears then it cannot access potentially out-of-date data. It may also be desirable for other users to also lose access to some or all of the data that they share with the terminating user.

[0062] If a user modifies data which is held in the cache to which it has access then that change should be forwarded to core. storage prior to a synchronisation or migration. One way to ensure this is to forward the changes as they occur, though the changes can be forwarded at a later date if so wished. It is permissible to not forward changes which can be assumed to give an indeterminate value to the data (either before or after the synchronisation), or for data which is no longer required.

[0063] Data can be speculatively fetched (also known as “prefetching”) without harm. This allows multiple data to be fetched on any single datum access, typically to exploit any form of additional or improved communication capacity within the data storage system or subsystem on the assumption that the user will require that data in the near future. The speculatively fetched data would typically be associated to one or more users as if the user had requested the data without a synchronisation occurring.

[0064] If a user has modified a datum in a cache and then attempts to perform an atomic operation (an indivisible read-modify-write) on that same modified datum without having performed a synchronisation, then the atomic operation can occur directly on the datum within the cache without having to notify core storage, any other users, any other caches, or indeed anything external to the affected cache itself. Typically the datum is associated with the user(s) as if the operation was non-atomic.

[0065] There are many ways to implement a coherence-free cache with varying degrees of complexity and performance. We present here one possible example of a tagging method. Other methods, using tags or otherwise, can be used and the behavior will change accordingly. The example given is in the context of a computer system, but can also be applied to other systems.

[0066] With reference to FIG. 2, in this example of a basic coherence-free cache in a shared-memory multithreading multiprocessor computer system 20 there is a collection of processors 21 which share a common main memory 12. Each processor has its own single coherence-free cache 10 and can execute multiple threads simultaneously, with all those threads able to have access to the cache. A thread is analogous to a “user” and the shared main memory is analogous to the “core storage”. The processor is the domain served by its cache, and hence the threads being executed by that processor are in the domain served by that cache.

[0067] There is a mechanism to allow migration of a thread from one processor to another. The cache will typically be either write-through or write-back and fulfil the appropriate forwarding requirements. Threads have identification codes each of which are unique within the processor on which they are running.

[0068] With reference to the flowchart 30 of FIG. 3, when a thread requests data transfer 31 and there is a cache miss 32 then if the transfer is a read 41 the data is fetched from main memory 34 and placed into the cache 35. The datum in the cache is then tagged 36 at least by the identification code of the requesting thread, or more optimally by the identification codes of all active threads within the same processor. All the threads whose codes have been tagged to the datum gain access rights to that datum 37. If there is a cache miss 32 and the requested transfer was a write 41 then the data is written to main memory 42 and in the case of an allocate on write condition 43, the data is stored in the cache 35.

[0069] A synchronisation can be defined by the use of an indivisible (read-modify-write) operation on a memory datum. Better definitions are possible, but this is sufficient for this example.

[0070] When a synchronisation occurs then the threads performing the synchronisation lose their access rights to all the data in the caches of their respective processors.

[0071] If any thread requests access to data, and that data is in the cache, then that thread will effectively see a cache miss if it fails to have access rights to that data 33. A cache hit will occur only if the data is present in the cache and the requesting thread has access rights to that data 37.

[0072] If a cache hit occurs and the data is not modified then no changes to the access rights of the datum occur 40.

[0073] If a cache hit occurs and the data becomes modified 38 by at least one thread then after writing back to the shared core memory 39 changes to access rights are made 36 in the same way as if a cache miss had occurred.

[0074] If a thread terminates or migrates away to a different processor then all threads lose access rights to any data to which the terminating or migrating thread had access rights.

[0075] It is permissible, but not a necessity, to allow hereditary access rights. If a thread (the “parent”) spawns another thread (the “child”) on the same processor then the child can acquire access rights to all the data to which the parent has access rights.

[0076] Further modifications and improvements may be added without departing from the scope of the invention herein described. 

1. A cache for use in caching data from shared memory in a parallel processing system characterised in that said cache comprises at least one tag associated with said cached data.
 2. A cache as claimed in claim 1 wherein said at least one tag comprises information relating to the access of said cached data selected from a list comprising: the identity of a processing thread; the identity of a user; the identity of a processor; and a null value.
 3. A cache as claimed in claim 2 wherein said information relating to the access of said cached data identifies an entity permitted to access the cached data.
 4. A cache as claimed in claims 2 to 3 wherein said information relating to the access of said cached data identifies an entity which has previously accessed the cached data.
 5. A cache as claimed in all previous claims which further comprises a tag setting means for modifying the contents of said at least one tag.
 6. A cache as claimed in all previous claims which further comprises: a tag comparing means for comparing the contents of said at least one tag with the identity of the requester of access to said cached data; and a data access means responsive to said tag comparing means for providing access to said cached data.
 7. A parallel processing system comprising: at least one processor; shared memory; and at least one cache as claimed in any previous claim.
 8. A system as claimed in claim 7 wherein each processor has exclusive use of its own cache.
 9. A method of caching data in a cache from shared memory in a parallel processing system comprising the step of caching data fetched from a shared memory in said cache characterised in that said cache comprises at least one tag associated with said cached data.
 10. A method as claimed in claim 9 further comprising the step of writing data from said cache to said shared memory.
 11. A method as claimed in claims 9 to 10 wherein said at least one tag comprises information relating to the access of said cached data selected from a list comprising: the identity of a processing thread; the identity of a user; the identity of a processor; and a null value.
 12. A method as claimed in claim 11 wherein said information relating to the access of said cached data identifies an entity permitted to access the cached data.
 13. A method as claimed in claims 11 to 12 which further comprises the step of a tag setting means modifying the contents of said at least one tag.
 14. A method as claimed in claim 13 which further comprises the step of: said tag setting means setting said at least one tag to the identity of the requester of a cache access.
 15. A method as claimed in claim 14 which further comprises the step of: said tag setting means setting said at least one tag to the identity of a plurality of the processes active on a processor.
 16. A method as claimed in claim 13 which further comprises the step of: said tag setting means setting said at least one tag to a null value.
 17. A method as claimed in claims 11 to 12 which further comprises the steps of: comparing the contents of said at least one tag with the identity of the requester of access to said cached data; and depending on the results of said comparison, providing access to said cached data
 18. A method as claimed in claim 9 wherein said at least one tag comprises information relating to the access of said cached data selected from a list comprising: the identity of a processing thread; the identity of a user; the identity of a processor; and a null value.
 19. A method as claimed in claim 18 wherein said information relating to the access of said cached data identifies an entity which has previously modified the cached data.
 20. A method as claimed in claim 19 which further comprises the steps of: comparing the contents of said at least one tag with the contents of another tag within said cache; and depending on the results of said comparison, writing data from said cache to said shared memory. 